*RMC13007 - 01/14/2008 - The Socket APPLDATA value is now generated for * LPR, Direct Socket and SMTP Socket activities. * The SMTP printing process now supports the use * of non-standard SMTP sockets. * *Enhancement Summary: *1. The ROPES IP Printing device type modules now provide more trace * information. Additional trace points include: * Before INITAPI * Before SETSOCKOPT * Before GETHOSTBYNAME * After GETHOSTBYNAME * Before CONNECT * Before IOCTL * After IOCTL * In addition, an IOCTL call has been added to supply the TCP/IP * APPLDATA information to be associated with the socket. The * APPLDATA information was introduced in z/OS V1R9 and is also * available in V1R7 and V1R8 by PTF. * "A new SIOCSAPPLDATA IOCTL is available that allows applications * owning stream (TCP) sockets to associate forty bytes of * application data with the socket. The associated application * data is made available on Netstat ALL/-A, ALLConn/-a and COnn/-c * reports, in SMF 119 TCP Connection Termination records and * though the Network Management Interface (NMI) on the * GetTCPListeners and GetConnectionDetail poll requests." * From the HOLD data for UK28303 (z/OS V1R8). * * The APPLDATA created by ROPES consists of 40 bytes defined as: * * Position Contents * 1 - 5 Literal "ROPES" * 7 - 10 Module Id (LPRP, MRDP, SOCP) * 12 - 15 Printer Id * 17 - 20 Device block suffix * 22 - 25 Data stream type * 27 - 34 Report Name * 36 - 40 Connection date (yyddd) * *2. The ROPES SMTP printing process now supports the use of an SMTP * server that is not listening on the standard port 25. * * The ROPES Device Block Sockets segment has had a new field added * to accomodate the SMTP server port number to be used when connect- * ing to the server. The ROPESDEV TYPE=SOCKETS macro instruction * now accepts the value SOKPORT=NNNNN, where NNNNN is a number in * range of 1 - 61439. The default value is still 25, the standard * SMTP port number, which will be used if the SOKPORT keyword is not * specified, or if the Device Block was created prior to V13. * * The anticipated use of this is to provide the ability to have * different ROPES SMTP printer tasks communicate with different * SMTP servers if you have the need to distribute your workload, * and to allow you to assign a non-standard port when you have * no other way, such as a firewall, to prevent the use of the * server for unintended purposes, for example, as an Open Relay * mail server for use by spammers and other unsavory types. * *Temporary Fix: * The following replacement object modules must be obtained from * technical support: * ROPEDRVR, ROPELPRP, ROPEMRDP, ROPESOCP * The following new source modules must be obtained from * technical support: * ROPEAPPL, ROPESDEV * *Documenation Changes: * The relevant documentation will be updated and incorporated in * the next release of the manuals. * *Permanent Fix: * This feature will be incorporated in the next release of * ROPES. * *End Of Document